HamCall (October 1991)/HamCall (Whitehall Publishing)(1991).bin/prgming/ada/aic44.doc

Text File | 1987-10-14 | 33KB | 629 lines

This file contains the most recent  issue of
the  Quarterly  AdaIC  newsletter; currently
the December, 1986 issue.
(AdaIC point of contact: Greg Kee)

                               Ada IC Newsletter

Volume IV, Number 4                                        December 1986


From the Director, AJPO

Dear Friends of Ada:

The Ada community has long awaited the publication of  a document  that
defines Ada compiler validation procedures.  I am pleased to announce that on
1 January 1987,  the Ada Compiler Validation Procedures  and Guidelines
document will be available to the community,  initially on the Ada IC
Bulletin  Board, and later through DTIC and NTIS distribution channels.
This document was distributed to Ada Board members and Ada Validation
Facility (AVF)  managers for final comment at the Charleston,  West Virginia
Ada Expo '86 in November.  Their comments, as well as  all the comments
received  during  the public review,  which began in February,  1986  were
taken into  consideration for this  final revision.  The document was
scrutinized by members of the Ada Board Evaluation  and Validation Panel and
AVF managers,  all of whom I would like to personally thank for their
outstanding  efforts and  support.   I  would  also  like  to  thank  all
those individuals in the Ada community who contributed to the evolution of
ideas that went into the  preparation of this document.   This was  truly a
community-wide effort for which we can all take credit and pride.

The document itself contains a list of terms and definitions  that  are
crucial to the understanding of the validation process.   Included in  this
document is an explanation of the Ada Certification body and its composition
and function; the concept of a derived compiler,  a new vehicle for compiler
validation aimed at fostering the growth  of  available Ada  compilers;  and
the  concept  of a project   validated   compiler,   which  allows   program
managers  sufficient flexibility in using and maintaining an Ada compiler
throughout the development and support of their programs.

This document also addresses the procedures for establishing an  AVF,
including performing  validation  responsibilities,  obtaining  and
maintaining  an  AVF charter,  and  supporting  periodic audits.   It also
addresses  the life cycle development  of  the Ada Compiler  Validation
Capability test  suite.  Finally, this document provides guidelines to
Service program managers on the use of Ada compilers,  without  mandating how
to  maintain  an  Ada  compiler's validation status throughout the life cycle
of a program.

This document  will  be reviewed,  updated and republished on  an annual
basis. Your comments and recommendations are welcome and should  be forwarded
directly to the AJPO.



Virginia L. Castor
Director
Ada Joint Program Office


Services Release Ada Policy

Air Force On September  29,  1986,  GEN Larry D.  Welch, Chief of Staff,
USAF,  signed AF Regulation  (AFR)   800-14,  the  Air Forces'  policy for
the  acquisition and support of  computer  resources.   As stated in AFR
800-14,  the  Air Force Ada policy is that  software developed for  major
systems and Air  Force Designated Acquisition Programs must be written in the
Ada programming language.   For all other programs, a Computer Resources
Working Group will consider the use of Ada and make a  formal recommendation
to  the program manager.   Only DoD validated compilers may be used.

Copies of AFR 800-14  are available from  Naval Publications  and Forms
Center, 5801  Tabor Avenue,  Philadelphia, PA 19120-5099.  Excerpts from AFR
800-14 are available electronically  on  the Ada20  and  AdaIC  Bulletin
Board  under the following  filename: AF-POL.HLP.

Army

During  AdaExpo  '86,  the  Army's  representative,  MAJ  GEN  A.B.
Salisbury, Commanding  General,   U.S.   Army  Information  Systems
Engineering  Command, mentioned the following points  concerning  the  Army's
policy  on  Ada.  Army Material  Command's (AMC)   policy  on  Ada will  be
that  Ada  is  the single programming language  to be used  in the
development, acquisition, deployment, and support or Battlefield Automated
Systems (BAS)  and joint systems for which the Army has lead on software.
All systems, even those for which a waiver has been granted,  must use an Ada
Program Description Language (PDL).  Information Systems Command (ISC)
policy on Ada is that all  software developed, acquired, or maintained by ISC
elements will use the Ada programming language and related tools.

AMC's policy is targeted for release in the form of a memorandum by the  end
of this year and a formal policy released at the beginning of next year.

ISC's policy was released in December 1984,  in the form of  ISC Bulletin
18-2, and is targeted for reissue at the end of this year.

Navy

On September 25,  1986,  ADM J.B.  Busey, Vice Chief of Naval Operations
signed OPNAVINST   5200.28,   the  Navy's  policy   on   Life   Cycle
Management  of Mission-Critical Computer Resources (MCCR)  for Navy Systems
managed  under the Research, Development and Acquisition (RDA) process.

The purpose of  this  instruction is  to establish policy for  the
acquisition, management and  life cycle support  of software and related
computer resources associated with Acquisition Category (ACAT) programs.  Ada
has been approved as the Navy's  general purpose standard  HOL for
mission-critical  systems  and is required for new developments and shall be
passed into use for existing systems at the next major upgrade.

Copies of  OPNAVINST 5200.28  are  available from Naval  Publications and
Forms Center,  5801  Tabor Avenue, Philadelphia, PA 19120-5099. An electronic
version will be  available on  the Ada20  and AdaIC Bulletin Board under  the
following filename: NAVY-POL.HLP.

MIL-STD CAIS Unanimously Approved By CAIS Standardization Working Group

The recommended changes to  the January 1985  version of  the  proposed
MIL-STD CAIS have been unanimously approved by the CAIS Standardization
Working Group. These changes were developed in direct  response to the formal
MIL-STD comment process  (discussed  in  the  May  AdaIC  newsletter),
input  from  prototype implementers,   and  informal  comments  from  the
government,  industry,  and international Ada communities.

The Standardization  Working Group recommended the revised CAIS  be  adopted
as DoD-STD 1838.   This is a significant milestone for the Ada  language,
which is the culmination of much effort by the KAPSE Interface Teams (KIT and
KITIA).

The standard should be available towards the end of the 1st calendar quarter
of 1987.   The next  Ada  IC  newsletter,  as  well  as  Ada  Today,  will
contain instructions on how and where to obtain this DoD-STD.

        RADC Seeks Beta Test Sites for Ada Compilation System

Beta  test  sites are being sought  for  RADC's  Ada  Compilation  System
(ACS) developed by  Intermetrics,  Inc.   The ACS runs  on  IBM 370,  43XX,
and 30XX computers as  well  as plug-compatible machines such  as those  made
by Amdahl. The UTS operating system (2.3)  is a UNIX variant and is available
from Amdahl either in "native mode"  for Amdahl 580-series machines or on top
of VM  on IBM machines.   Over 98%  of the Ada  Compilation  System  is
written  in  Ada and consists of approximately 400,000 lines of source code.

The compiler has been validated with ACVC 1.8 and executes at 250 to 400 lpm
on the IBM 4341  with an Ada to assembly language expansion ratio of 1  to 4.
The compiler  also  contains  a comprehensive global  optimizer.   It
performs four major  classes   of  optimizations:    Ada-specific
optimizations   (such  as constraint-check   minimization   and
Haberman-Nassi    Tasking),   classical optimizations  (such  as   common
subexpression  elimination  and   dead  code elimination),  register
optimization  and branch  optimization.  Other compiler features include a
partial implementation of the Ada  Reference Manual, Chapter Thirteen,
extensive  syntax error recovery,  compilation statistics gathering, and
generation of source, object and symbol/cross-reference listings.

Because of the emphasis on optimization,  configuration management support,
and capacity,   the  ACS  is  suitable  for  developing  large,
time-critical  Ada applications.   The ACS was developed in accordance with
the Military Standards for software development, and is documented.

One week User and Maintenance courses will be given  in the Jan  87 time
frame. RADC focal point is Donald L. Mark, AV 587-3655 or commercial (315)
330-3655.

Ada Language System / Navy

In February, 1981, the Chief of Naval Operations, designated the Naval
Material Command as the Principal Development Activity  (PDA)  charged with
implementing Ada capability for use in developing Navy  mission critical
systems.  Prior to 1975,   when  the   Department  of   Defense   computer
programming  language standardization  program was initiated,
government-developed  computer systems were affected  significantly by the
lack of integrated,  high quality software tools and the computing
environment required to support them.   The goal of the standardization
program is to establish a  single high order language,  Ada, to be used by
DoD computing systems.

The Army-developed  Ada Language  System  (ALS),  validated  by  the  Ada
Joint Program Office  in  December,  1984,  is  the development  baseline
adopted to enhance production  of  Ada  support  environments  for  the
Navy.  Full-scale engineering development  (FSED)  capabilities  in  Ada  are
expected  by 1989. Development  of  Ada environments  will be accomplished
by related development efforts,  each composed of two distinct  segments --
a Minimal Ada Programming Support Environment (MAPSE) and an Ada Run-Time
Environment (RTE).

The  major functions of  MAPSE will  provide for Ada compilation  facilities
to generate programs  for standard  embedded computers,  text editors,
formatters, report generators  and configuration management  tools,  Kernal
Ada Programming Support Environment (KAPSE), and data base support for these
functions.

The RTE functions will be developed to meet hardware  and mission
requirements, which  require  intensive  application  of  extant  programming
technology for development of reliable and efficient tools.

The Navy's first development efforts will result in the availability of a
pilot production  capability  for the AN/UYK-44,  a Navy  standard embedded
computer. Full  Ada  production  capabilities  for  the  AN/UYK-44,
AN/AYK-14,  and  the An/UYK-43 computers will be the result of subsequent
development efforts.

Second Annual ASEET Symposium Call for Papers

A Call for papers has been issued for the  Second Annual ASEET Symposium  to
be held in  Dallas,  Texas,  June 9  -  11,  1987.  Both  formal  paper  and
panel discussion sessions are planned.  Papers and panels are solicited  in
the areas related to Ada software engineering  education and training
including, but not limited to:

      o Lessons Learned
      o New Education and Training Concepts
      o Teaching Ada in the University
      o Ada Professionalism/Certification
      o Education for the Educator (Teaching the Teacher)
      o Ada Education for the Manager

Four copies of papers or panel proposals should be sent  by January  1, 1987
to Catherine  McDonald,  IDA,  1801  N.  Beauregard Street,  Alexandria, VA
22311. Authors will be notified of acceptance by  February 1,  1987. Camera
ready copy will be required by May 1, 1987.

Ada in Ebbedded and Real-Time Systems


F4-J Weapon System Trainer
Science Applications International Corporation (SAIC)
POC:  Mr. James D. Magnusson
[phone]

In 1982 Science Applications International Corporation was selected to
perform the F4-J Weapon System  Trainer modernization program for the  US
Navy.   This program  consisted   of  replacing   the   computational   and
the  real-time input/output  hardware  for   the   F4-J  Weapon   System
Trainers   and  the reprogramming of  the trainers  using FORTRAN.   As  an
internal  research and development  project,  SAIC  undertook  an  automated
conversion  of  the F4-J real-time software from FORTRAN to Ada.  The goals
of the project included  the demonstration  of  Ada  in  a  complex,
real-time  computer  system  and  the development  of  techniques  for
handling  real-time  I/O  using  Ada.  Flight simulators  are characterized
by  their intense  input/output  requirements for fidelity of the simulation.
A large number of signals must be transmitted  at precise times and at high
rates.

SAIC  used  a Gould 32/6780  to develop and translate  the  code,  and  a
Gould 32/8780  with five megabytes of memory and 64K cache to run the
simulator. The Irvine Compiler Corporation's (ICC)  compiler,  Version 2.2
(not validated) was used.   A shared memory segment was added to the UTX
operating  system to allow processes to communicate in real-time.   Also, two
system procedures were added to  UTX to  support the real-time input/output
requirements  of the simulator. Upon completion, the F4-J software consisted
of over 150,000 lines of Ada code.


SAIC found the results of  this  project encouraging.   The  system
integration phase proceeded more rapidly and with  fewer errors  encountered
than  with the FORTRAN version.   Several errors in the FORTRAN code were
detected  by the Ada compiler during  the compilation process.   One  of the
unexpected results was that the final Ada version required less memory space
than the FORTRAN version.


The  Naval  Training  Support  Center  (NTSC)  actively  participated  in
this experiment by  providing access  to  the F4-J  simulator  at  Oceana
Naval Air Station and witnessing the real-time demonstration of the Ada
system during the week of  March 11,  1985.   Timing measurements  made
during the demonstration indicated  that  the Ada version took  significantly
longer  to perform certain operations due to the use of double precision
calculations by the ICC compiler. However,  Naval test personnel that
participated in the  demonstration were not able to distinguish between the
flight performance and operation of the Ada and FORTRAN versions.

Beech-Starship
Rockwell Collins
POC:  Mr. Dave Funk
 [phone]

Software for  the Beech Starship,  a twin engine  turbo-prop business
aircraft, was developed by Rockwell Collins on  a VAX host  using a compiler
modified by Collins.   The software was targeted to the Intel 80186, where it
was run using the Irvine Compiler Corporation compiler.   Software was
written in Ada for two subsystems:  the Electronic Flight  Display,  and the
Flight Management System. Rockwell was not mandated  to  use Ada;  rather,
the  initiative  was taken by Rockwell  to  use   Ada  because  of  good
experiences   with  previous  Ada applications.   The  Electronic  Flight
Display subsystem  includes two primary flight displays,  two  navigational
display,  an  engine  and  instrument crew advisory display,  and a
multifunction display.  The  Flight  Management System accepts  input from
navigation  radio  and   provides  as  output  lateral and vertical
positioning data and navigation radio tuning.

This effort produced a total of 82K lines of  Ada code,  31K lines  of Ada
code for the Electronic  Flight  Display,  which was comprised of  8  tasks,
and 51K lines for the Flight  Management  System,  comprised  of  20  tasks.
Since the compiler used did not support full Ada tasking, Rockwell built its
own run-time executive to perform a priority driven event model.   Tasks  for
these  systems ran at rates of 100, 50 and 20 Hz.

Training  for  this  effort  was   accomplished  in  house   and  consisted
of approximately  6  days  of  classroom  instruction,  with  additional
hands-on instruction outside the  classroom.   Regarding  use  of  the  Ada
language to implement this project,  software developers at Rockwell Collins
felt that the additional time required to perform compilations  using Ada was
more  than made up for by the reduction in  debugging time which  resulted.
The Beech-Starship aircraft  has  been  in  flight  testing   by  Beech
since  early   1986,  and certification by the FAA for regular commercial
operation is imminent.

Fault-Tolerant Distributed Operating System
Westinghouse Electric Corporation
POC:  Mr. Doug Ferguson
[phone]

Westinghouse has developed software  in  Ada for  a  fault-tolerant
distributed operating system to manage a distributed processing system.  The
fault-tolerant function of the operating system provides the capability to
continue execution of application processes after the failure of  one or
more processing modules. The distributed processing system,  upon which a
version  of the fault-tolerant portion of  the code  was executed,  consists
of three  1750A processor modules which communicate  with  each  other  over
a  common  16-bit  transaction bus. Functions  of  the distributed  operating
system  include  process scheduling, communications, input handling, and
fault tolerance.

The  distributed operating system  (DOS)  was designed on  the light
helicopter experimental project for Boeing,  Inc.   During April 1986,  a
demonstration of the  fault tolerance portion of  this  operating system  was
performed  at thecritical design review.  Since that time, Westinghouse,
under Internal Research and Development, has implemented over 80 percent of
the DOS design in Ada.  The target architecture of DOS is the Westinghouse
signal processor  in addition to architectures similar  to that of  PAVE
Pillar.   A parallel multidrop internal bus,  known  as  the PI-bus,
interconnects  general purpose 1750A  CPUs, array processors,  memory
modules,  and external bus interface  modules.  Sensor and video data is
transferred over the high-speed interconnect.  The DOS resides in all
modules,  ensuring fault tolerance over the distributed architecture.  When a
module of any type fails,  the distributed executive of  DOS reconfigures the
system ensuring the least possible system downtime.

As of  September 1986,  the  PI-bus communications and process  scheduling
have been implemented and tested.  The complete DOS will be completed for the
V1750A CPUs  by  March  1987   and  for  the  entire   Westinghouse  signal
processor architecture including the array processors by November 1987.

Ada & AFATDS
Magnavox Electronics Systems Co.
POC: Mr. Skip Carstensen
[phone]

Magnavox  recently  completed a third software  release for the  Advanced
Field Artillery Tactical Data System (AFATDS).   Upon full implementation,
the AFATDS will integrate all fire support functions for Army field
artillery. The software,  consisting of 770,000  lines of source code,  is
hosted on a VAX under VMS and targeted to  multiprocessor MC68020-based
workstation.  The code for this embedded target is written in Ada using the
DEC Ada compilation system and  the TeleSoft  second  generation compiler,
except for 4000  lines of code written in assembly.   It is anticipated that
in the near  future, the assembly code will  be  replaced entirely with  Ada.
Major functions of AFATDS include information and data management,
communications support (local area networking with ISO model and IEEE
standard token ring), communications interface (to most military media; wire
and radio), fire support execution, fire support planning, artillery
movement,   message  processing,   tactical  displays,  and  status
reporting.

In testing of  the Release 3  of AFATDS  software,  493,000 lines of  code
were tested (using 4986 discrete tests), revealing only 38 software problems,
or 99% reliability.   Programmer productivity for the AFATDS project averaged
11 lines of code (LOC)/day/person during Phase 1,  32 LOC/day/person during
Phase 2, and 38  lines of code/day/person during phase 3.   Programmers
received three weeks of intensive software   engineering with Ada, and
additional training in Object Oriented   Development.   Additional training
included classes in Ada  for SQA personnel and Ada test methods.

Operational Flight Program (OFP) For F-16
Data Entry/Cockpit Interface System
General Dynamics
POC:  Mr. J.P. Sarkar
(817) 777- 4733

General Dynamics has produced a flyable Ada OFP for the F-16 Data
Entry/Cockpit Interface System (DE/CIS).    Because previous airborne
evaluations of Ada have stressed  real  variable  processing  such   as
flight   control   and  other algorithm-intensive   processing,   General
Dynamics  elected  to   produce  a real-time, pilot-performance-critical OFP
that stresses the logical and display processing.

The DE/CIS  application provides  the  interface  between  the  pilot  and
such avionics as the voice-interactive system, control panel, side-stick
controller, keyboard,  and display.   Real-time requirements include a  few
microseconds to process in  analog-to-digital conversions.   This nearly
full  Ada OFP, having only 7% of non-Ada code, contains portable modules.
The reusability of non-I/O modules can be accomplished by using the Ada for a
different target machine.

              ** Validated compilers list as of 1 January 1987.**
                  ** Please see the file: VAL-COMP.HLP for **
                 ** the January 1, 1987 validated compilers. **


Ada
? ? ?    Questions & Answers     ? ? ?

The following are a list of questions that are commonly  asked of  the AJPO
and the AdaIC.

Dear AJPO:   Is a design language or design language guide which is a subset
of the Ada language allowed to use the Ada trademark as part of the title?

Answer:  Describing, advertising, or promoting a language processor as an
"Ada" processor  is  equivalent  to  making  a voluntary statement of
conformance to ANSI/MIL-STD-1815A-1983.  However,  the  term  "Ada"  may be
used in describing language processors  which are not completely  conforming
or are  not making a claim of conformance provided that there is a precise,
easily visible statement of their non-conformance at  the same  time  and in
the  same  context.  Those persons advertising,  offering for sale, or
otherwise promoting an Ada language processor  which is  not a complete
implementation  of  the  Ada  language are required to provide  the Ada Joint
Program Office  with  evidence sufficient to demonstrate  that  such
portions of the Ada language  asserted  as implemented conform to the Ada
Standard.

The trademark "Ada"  may  also  be  used in connection  with manuals,
leaflets, brochures,  books,  and other  documents  concerned  with  the  Ada
programming language,  provided it is used  in accordance with  the
"Guidelines For  Use of Trademark Ada"  produced by the Ada Joint Program
Office.  These guidelines are available from the Ada Information
Clearinghouse upon request.

? ? ?

Dear AJPO:  What Date have you set for completion of Ada Implementation?

Answer:   As Ada related technology becomes widely disseminated,  there will
be continued  maintenance and upgrading  of  the  DoD  infrastructure  to
maintain technological  currency.   These  DoD  investments  will  be
appropriate  as a cost-effective means for improving software production
processes.

In this sense, the Ada program will continue to go on so long as we continue
to use Ada.   Given the normal 30  year life-cycle for programming
languages, Ada should continue until at least 2005.

However, the current accelerated emphasis on Ada Technology Insertion should
be completed by 1995.   According to a recent Institute for Defense Analysis
(IDA) study *  we  will be beyond  the 'hump'  of added costs needed to
expedite the insertion of new Ada technology by that time.

? ? ?

Dear AJPO: Do  you have  any estimate of savings that  might accrue  from Ada
implementation?

Answer:   According to recent IDA study* the cumulative ten-year cost
reduction in DoD MCCR expenditures from 1985  -  1995 attributable to Ada and
Ada related technology is approximately $57 billion

$7.35  billion  is  attributable  to institutionalizing the re-use  of
software products that is possible with Ada.

$49.2  billion comes  from  the  reduction  of  labor  effort  due  to
improved practices   and  technology  during  the  software  development  &
maintenance activity.

*IDA paper P-1930, Cost Benefit Study on Ada, June 1986

ASEET Advanced Ada Workshop

The Ada Software Engineering Education  and Training (ASEET)  Team sponsored
by the Ada Joint Program Office is conducting an Advanced Ada Workshop to  be
held January 12-16,  1987  at Keesler AFB, Mississippi. The workshop will
provide an opportunity  for  educators/trainers  to  further  their
understanding  of Ada Software Engineering principles and practices. For
additional information or to make your reservation, please call one of the
following Team members:

1st Lt Tony Dominice or Capt. Thana Ross
ASEET Advanced Ada Workshop
3390 TCHTG/TTMKPA
Keesler AFB, MS 39534-5000
Net Mail: DSAMUELS@ADA20
Phone [phone]/3907


Ada Information Available through AdaIC Bulletin Board

The  Ada  Information  Bulletin  Board  is  a  publicly   available  source
of information  on the  Ada language and  Ada activities.   This Bulletin
Board is used by the AdaIC to announce  current events,  general activities
and indicate the  status  of  various Ada compiler  efforts.   Access to  the
Bulletin Board requires a computer terminal and modem.

Data: [phone]  Voice: [phone]
Telecommunications Setup Information:
300/1200 Baud; No Parity; 8 data bits;  1 stop bit

If the line is busy, the user should try again.  If the system does not
respond immediately,  enter three carriage returns slowly.   Once the system
responds, please  follow  the instructions as  indicated.   To read  a file
it  must be downloaded to a local PC using straght ASCII or XMODEM protocol.
User sessions are limited to 30 minutes to accomodate the greatest number of
users.


Ada Events Calendar

The Ada Events Calendar   includes information on upcoming  Ada activities
such as classes,  seminars  and conferences.   The  Ada   Calendar  lists
only those programs with fixed  dates and will  not   include programs which
are on-going. The   information herein is provided   for informational
purposes and  does not represent an  endorsement of   these events by the
AdaIC or the  AJPO.  If you would  like  to  have  your  Ada-related   event
included  in  future  AdaIC Newsletters,  contact the Ada Information
Clearinghouse at  [phone] or [phone].



January 1987

  7-9  AdaUK Sixth Annual Conference.   Theme:  Ada - The Infrastructure.
POC: Helen Byard, Computer Science Dept., Univeristy of York, York Y01 5DD,
ENGLAND, 0904-412740.

12-16    ASEET Advanced Ada Workshop,   Keesler AFB, Mississippi, POC:  1st Lt
Tony  Dominice  or  Capt.  Thana  Ross,  3390  TCHTG/TTMKPA,  Keesler  AFB,
MS 39534-5000, [phone]/3928/3907.

12-16    AdaJUG  and  SIGAda  Conference,  Ft.  Lauderdale,  FL.   POC:  Donna
Whisman, Gould, [phone].

14-16    Workshop on  Ada Applications  in  Mission Critical  Defense Systems,
sponsored by IEEE Computer Society,  Jersey Coast Chapter, U.S. Army CECOM,
and Monmouth College.   POC:   Howard Hamer, [phone], AV 995-2253; or
Dr. Ed McCrohen [phone].


February 1987

9    Front Range Ada Working  Group  (FRAWG)  Meeting,  Denver  Colorado.
POC: Robert Lewis, Martin Marietta, PO Box 179, Denver, CO 80201, (303)
971-6731.




March 1987

2-3    Methodologies and Tools for Real-Time  Systems,  Tysons  Corner,  VA,
POC: National Institute for Software, [phone] or [phone].

4-5    Software  Reuseablility  and  Maintainability,  Tysons  Corner,  VA,
POC: National Institute for Software, [phone] or [phone].

16-19    Fifth National  Conference  on Ada Technology,  Fourth Washington Ada
Symposium, Arlington, VA, POC:  Joint National Conference on Ada Technology,
US Army   Communications-Electronics   Command,    ATTN:   AMSEL-SDSC-SS
(Albert Rodriguez), Fort Monmouth, NJ 07703, [phone].


May 1987

13-15    Workshop  on  Real  Time  Ada   Issues,   sponsored  by   Ada  UK  in
collaboration with SIGAda.  POC:  Anthony Gargaro, Computer Sciences Corp.,
304 West Route 38,  Moorestown,  NJ  08057, [phone]; or Helen Byard
Computer Science Dept., University of York, York Y01 5DD, ENGLAND,
0904-412740.

26-28    Ada  Europe   Conference  (Ada  Components:   Libraries  and  Tools),
Stockholm,  Sweden.   POC:  Prof.  Sven Tafvelin, Dept. of Computer
Technology, Chalmers University of Technology, S-4192 96 Gothenburg, Sweden.


Ada Information Clearinghouse          Ada Joint Program Office
3D139 (1211 Fern., C107)               3D139 (1211 Fern., C107)
The Pentagon                           The Pentagon
Washington, DC 20301-3081              Washington, DC 20301-3081
[phone]                         [phone]
                                       AV 224-0210

The Ada Joint Program Office has  the responsibility for  managing DoD's
effort to implement, introduce, and provide life-cycle support for the Ada
programming language,  the DoD's common high-order  language for  Mission
Critical Computer Resources.   The  Ada Information  Clearinghouse
facilitates  the  transfer of timely  information between the Ada  Joint
Program  Office  and  the  Ada User Community.   The  Clearinghouse
coordinates  the  collection,  integration and distribution of documentation
on all aspects of the Ada language and associated aspects of DoD's Software
Initiative,  announces recent activities  and general information on Ada via
the  Ada20  or RBBS,  and provides recent updates on Ada conferences,
seminars, classes and textbooks.


                 AJPO Staff Expands

At  the Ada Expo  '86  conference in  West  Virginia,  Ms.
Virginia L. Castor, Director of the Ada Joint Program Office,  announced
three new additions to the Ada Joint Program Office  and reviewed the  areas
of responsibility of  each of her staff members.   Joining Ms.  Castor, LTC
David Taylor, Maj Allan Kopp, and LCDR  Philip  Myers are:  Ms.  Barbara
Fleming,  Mr. Sebastian Romano, Mr. John Stanton, and Mr. Raymond McGlynn.

Barbara Fleming comes to  the AJPO  from  Defense  Communications  Agency
(DCA) Joint Data Systems  Support Center (JDSSC),  where she was  Project
Officer for the reimplementation of data communications software  in Ada.
Prior to taking over  as  Project Officer she worked  on  the  Worldwide
Military  Command and Control System (WWMCCS) Graphics Program managing a
component of that program.

Sebastian (Bardie)  Romano comes to the AJPO from the Naval Air Systems
Command where  he   held  the  position   as  Section  Head,   Computer
Resources  for Anti-submarine Platforms.  He was involved in the procurement,
development, and support of tactical embedded computer resources  for a wide
range of platforms including  the P-3C,  S-3A/B,  SH-60B/F,  E-2C,  and the
AMBER  remote piloted vehicle.   His knowledge  of  and  experience  with
mission  critical computer resources and  embedded computer applications  are
appropriate at  this time as Ada is being introduced into major defense
weapons systems.

John Stanton comes to the AJPO from General Services Administration (GSA)
where he implemented and managed GSA's  Ada  Validation  Facility  and  other
federal standard language validation systems.

Raymond McGlynn comes to  the AJPO  from  U.S.  Army Communications
Electronics Command  (CECOM)  where  he  was  responsible  for  coordinating
the  Software Management Control  System (SMCS)  activities and has
participated  in the IEEE Working Group on  Ada as  a Design  Language.   He
was  also  involved  in the coordinating  the  technical  evaluation  of
contract  proposals  for  the Ada designed DDN X.25 VLSI/VHSIC interface.